Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1033

reference: 267-tree-1
name: 1033
tree-preservation-order: undefined
267-tpo-1
uprn
address-text
point: POINT (-0.938148 50.858811)
geometry: MULTIPOLYGON (((-0.938092 50.858805,-0.938094 50.858816,-0.938102 50.858826,-0.938114 50.858834,-0.938130 50.858839,-0.938148 50.858841,-0.938165 50.858840,-0.938181 50.858835,-0.938194 50.858827,-0.938202 50.858817,-0.938205 50.858806,-0.938203 50.858795,-0.938195 50.858784,-0.938183 50.858776,-0.938167 50.858771,-0.938149 50.858769,-0.938132 50.858771,-0.938116 50.858776,-0.938103 50.858784,-0.938095 50.858794,-0.938092 50.858805)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL